collection

1.3. Vendor 3 Results

Comments from Vendor 3.

  1. Vendor 2 and Vendor 1 can retrieve EVENT REQUEST messages from Vendor 3 Server — But they would prefer that the Vendor 3 IMIP messages come in the “multipart/mixed” MIME format. We have included this item in our bug list.

  2. We tried to import a REPLY from the other vendors. We were able to import Vendor 2’s REPLY. However, we could not import Vendor 1’s REPLY messages. This was because they were inserting the Recurrence-ID in the event REPLY message even though it was a non-recurring VEVENT. Also, we had a bug in handling RSVP. We were saving the change in the RSVP value of the attendee, which caused a UI bug. (In our User Interface, the attendee was moved to an INFORM)

  3. Vendor 1 and 2 can receive our recurring EVENT REQUEST invitations.

  4. We can import Vendor 1 and 2’s recurring REPLY messages. However, we get the same number of e-mails as instances (i.e. 60 replies (messages) to 1 recurring event)

  5. We can import CANCEL messages from Vendor 1

  6. Vendor 2 could not import our mail messages from a Spanish or French user. — Vendor 1 can display them OK using the Eudora mail program.

  7. We can import a recurring REQUEST from Vendor 2

  8. Vendor 4 created an event. They sent two REQUEST messages, sequence=0, sequence=1, the first one sent RECURRENCE-ID, the second one did not. This is Vendor 1’s bug, and they may have fixed it.

What about others:

  1. No one implemented ADD.

  2. No one tested COUNTER or DECLINECOUNTER

The Vendor 3 team is working on fixing CalConnect-related bugs and will include the fixes in future releases.